Set CI B2_CI_VERSION=0 #127
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I don't it matters much here since this repo does not have appveyor enabled at the moment. |
To be thorough, the update could be merged anyway. for future use. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
Going back some years, boostorg/boost-ci provided a new way to configure B2 variables, which takes effect using B2_CI_VERSION=1. For example:
(new) 'B2_LINKFLAGS': '-fuse-ld=gold'
instead of
(previous) 'B2_LINKFLAGS': 'linkflags=-fuse-ld=gold'
Now that most boost libraries have migrated, we'd like to standardize boost-ci onto B2_CI_VERSION=1.
You can opt-out by configuring B2_CI_VERSION=0 and then upgrade later.
This pull request sets B2_CI_VERSION=0, so CI will continue to work, using the previous method.